home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19941031-19941221
/
000102_news@columbia.edu_Wed Nov 9 13:52:21 1994.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA09338
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 9 Nov 1994 22:40:40 -0500
Received: by apakabar.cc.columbia.edu id AA05208
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 9 Nov 1994 22:40:39 -0500
Path: news.columbia.edu!sol.ctr.columbia.edu!news.kei.com!news.mathworks.com!news.duke.edu!convex!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: C-Kermit vs MS-Kermit
Message-Id: <1994Nov9.195221.32422@cc.usu.edu>
Date: 9 Nov 94 19:52:21 MDT
References: <Pine.SUN.3.90.941106143639.22421D-100000@blue> <39mf2a$lpf@apakabar.cc.columbia.edu> <39r47t$pil@burgundy.csn.net>
Organization: Utah State University
Lines: 39
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <39r47t$pil@burgundy.csn.net>, oberg@teal.csn.org (Craig Oberg)
writes:
> fdc@fdc.cc.columbia.edu (Frank da Cruz) writes:
>
>>In article <Pine.SUN.3.90.941106143639.22421D-100000@blue> "Archimedes L.
>>Trajano" <cs932070@ariel.cs.yorku.ca> writes:
>>> Is it not possible to create an MS-DOS version of Kermit from the
>>> C-Kermit source files?
>>>
>>Maybe, but why bother? It would be bigger, slower, and do less, except
>>for some of the script programming features. With some care, it is quite
>>possible to write script programs that are portable between MS-DOS
>>Kermit and C-Kermit. I'm not denigrating C-Kermit at all, but really,
>>when you consider how much functionality is packed into the 200K-or-so
>>MS-DOS Kermit executable, it's astounding.
>
> For my use, the script programming is one of the MOST important
> features of MS-kermit and C-Kermit. I would love to have the the
> C-kermit and MS-Kermit scripting interfaces be 100% compatible
> (except for those limited by the OS). Perhaps there could be a
> way to link the C-kermit scripting source in to the MS-kermit
> version with out increasing the size dramaticly. If this is not
> possible or wise, then I would request to enhance the MS-kermit's
> scripting features to be compatible with C-kermit. For me, I
> would trade a lot of the size to get compatibility and readability
> of MS-kermit scripts.
----------
I'm sorry, but MSK and CK are not code compatible at all.
The command parsers which you like so much are extremely complicated
sets of code in each program, and they are very different. There will
be operations in one which are either awkward to implement in the
other or just can't be because of internal design considerations.
We try to make the two behave similarly, but there are limits on
program effects as well as person time involved (and I want to
emphasize that this means a *lot* of concentrated effort).
I don't understand your last sentence. I can say that we won't
trade lots of program space (memory) for seldom used features. But then
we don't have any idea of what's important to you.
Joe D.